FirstClass LogScan is a utility which analyzes FirstClass daily logs to produce a report in the following format (the report is visible here only if you read this file using TeachText):
Users are listed in the order of their calls to the BBS during the report period. The user list in this report has been abridged for the sake of space.
FirstClass LogScan can run either automatically, processing the previous day's log file and putting its report in the FirstClass LogFiles folder, or under user control, processing log files one at a time. In automatic mode, you can set it to write an abbreviated report -- just the top of the full report -- to a folder of your choosing. I use this feature to have it maintain a daily report of board activity in an external file accessible to my users. For this I use QuicKeys to automatically launch it at about 4 a.m. every day.
You configure FirstClass LogScan by launching it while holding down the mouse button. When you do so, you will see the following dialog (the dialog is visible here only if you read this file using TeachText):
The first text field holds the path to your FirstClass log files. It should be the same as what's shown except your volume name will be different. To set it properly, click the Find button and show FirstClass LogScan where the folder is.
The second text field is the location where you want FirstClass LogScan to put its brief report (use the second Find button to set the path), whose name you set in the third text field.
The fourth text field is the creator you would like to use for text files. This is a four-letter resource type which tells the document which parent application to launch if you double click it. Some common creator types are
MSWD Microsoft Word
MACA MacWrite
EDIT Edit
QED1 QUED
ttxt TeachText
The next 12 text fields are the numbers of sessions you don't want to include in the report. I have set sessions 3 and 4 to be ignored, since they are network accounts which I don't care about tracking. If you don't want to omit any sessions leave all these fields empty. If you have more than 12 network users you'd like to omit, send me a very pleasant note and I might oblige you. FirstClass numbers its sessions beginning with 0. I believe that network sessions are always the highest numbers in the series-- at least that's how it works on my board.
The three check boxes let you set the following:
MultiFinder -- enable this check box if you're using MultiFinder or System 7 (or later).
Automatic -- enable this check box if you want FirstClass LogScan to run automatically rather than under user control. If you want to use it both ways, use two copies of the utility, one set for Automatic, one not.
Brief Report -- if you don't want to create a Brief Report, disable this checkbox.
Click the Save button to save your configuration. Cancel discards your changes.
When it runs, FirstClass LogScan reads a text file called "LogScan Header" (without the quotes) located at the same directory level as FirstClass LogScan to get the legend for its report. The contents of my LogScan Header file are as follows:
Line 1 = (213) 254-4852
Line 2 = (213) 254-4133
Line 3 = MacValley
For best results, view with Monaco 9 pt. X is busy . is idle
Obviously, you want to change your version of this file to reflect your own phone number(s). You can put up to 255 characters in this file. If you put more, only the first 255 characters will be read.
In addition to these configuration options, all of FirstClass LogScan's prompts and settings are stored in its STR# resources, so if you're handy with ResEdit you can customize it as you wish.
The best way to get everything working is to use a copy of FirstClass LogScan with the Automatic box unchecked. Prepare your LogScan Header file (it must be text, not a formatted word processing document) and run FirstClass LogScan, then check the results.
When FirstClass LogScan runs in manual mode, it presents you with a standard file dialog asking you to select a daily log to process. Select a valid FirstClass log file (if you decide to feed it something else it will do strange and messy things, though it won't alter the source file). Then it will ask you where to save its report, using what name. If you answer this in a rational and positive manner, it will analyze the input file and write a report. Then it will ask you for another file to process. Click Cancel when you're ready to quit.
When FirstClass LogScan runs in automatic mode it opens the previous day's log file, analyzes it and writes a report with the log name followed by the string " Report" to the FirstClass LogFiles folder. If you've enabled the Brief Report option, it also writes a short version (without the user names) to the location you've selected.
The graphic indication of BBS use shows activity in 20-minute divisions. An X indicates a valid session. A period (.) indicates no activity. If a caller logs on for even one minute in a 20-minute period that's enough to mark that time division. So a solid row of Xs does not necessarily mean your board was continuously busy, just that it received at least one call every 20 minutes. A better measure of board activity is in the percentages kept for each line, but the graphic display shows you when your board is busiest.
For the incurably curious, here are some notes on the STR# resources in FirstClass LogScan (the program substitutes appropriate data into the lines which contain ^0, ^1, ^2 etc.) :
STR# 128 holds report settings as follows:
#1 two-character string with Call symbol and NoCall symbol
#2 title string: BBS activity from ^0 to ^1
#3 summary: ^0 Graphic Interface calls, ^1 Command Line Interface calls, ^2 total
#4 Header file name
#5 "Line"
#6 "time used"
#7 "Connection speeds"
#8 "Registrations"
#9 "Name Calls Time"
#10 "Total"
#11 Sessions to omit, comma separated. Can contain up to 12 sessions
